DM-45049: Add support for SSL/TLS in the Qserv Czar frontend #859
+1,092
−514
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This effort is about replacing the non-encrypted HTTP protocol with HTTPS in the Qserv Czar front end: https://confluence.lsstcorp.org/display/DM/HTTP+frontend+of+Qserv
The new implementation of the front end’s REST API will be based on the built-in HTTP server https://github.com/yhirose/cpp-httplib added to Qserv in DM-44780.
No changes to the functionality of the front end are expected to be made. No modifications to the REST API version will be made either. The user documentation on the REST API will be updated accordingly.
The implementation provides two options for the SSL certificates: